Excluding specific application traffic from customer consumption data

ABSTRACT

Techniques disclosed herein include systems and methods for excluding specific application traffic from customer consumption-based data billing counts. This is useful for excluding traffic from consumption totals where the application traffic has been accounted for using other means, such as through billing as a separate or technically distinct service. In practice, a tablet computer (or other end user device) can run a video application that uses a high-speed data network via a cable modem. This video application may be included as part of a core video package associated with a distinct cable television service. The system then provides accurate consumption billing of customer traffic that is outside of any other managed services by creating separate logical data service flows at a Cable Modem Termination System (CMTS) for excluding specific traffic counts.

RELATED APPLICATIONS

This application is a continuation of earlier filed U.S. patentapplication Ser. No. 15/341,405 entitled “EXCLUDING SPECIFIC APPLICATIONTRAFFIC FROM CUSTOMER CONSUMPTION DATA,” (Attorney Docket No.TWC11-04(11-45C3)CON3, filed on Nov. 2, 2016, the entire teachings ofwhich are incorporated herein by this reference.

U.S. patent application Ser. No. 15/341,405 is a continuation of earlierfiled U.S. patent application Ser. No. 14/867,180 entitled “EXCLUDINGSPECIFIC APPLICATION TRAFFIC FROM CUSTOMER CONSUMPTION DATA,” (AttorneyDocket No. TWC11-04(11-45C2)CON2, filed on Sep. 28, 2015, the entireteachings of which are incorporated herein by this reference.

U.S. patent application Ser. No. 14/867,180 is a continuation of earlierfiled U.S. patent application Ser. No. 14/261,103 entitled “EXCLUDINGSPECIFIC APPLICATION TRAFFIC FROM CUSTOMER CONSUMPTION DATA,” (AttorneyDocket No. TWC11-04(11-45C1)CON, filed on Apr. 24, 2014, the entireteachings of which are incorporated herein by this reference. U.S.patent application Ser. No. 14/261,103 is a continuation of earlierfiled U.S. patent application Ser. No. 13/342,727 entitled “EXCLUDINGSPECIFIC APPLICATION TRAFFIC FROM CUSTOMER CONSUMPTION DATA,” (AttorneyDocket No. TWC11-04(11-45), filed on Jan. 3, 2012, the entire teachingsof which are incorporated herein by this reference.

BACKGROUND

The present disclosure relates to content delivery systems and billingsystems for such content delivery systems including cable and Internetdata communications services.

A significant portion of Internet service plans provide Internetconnectivity through a cable modem. Such Internet connectivity is oftenprovided by a cable TV service provider. It is common for suchcable-based Internet service to be provided along with conventionalcable television service. For example, a single coaxial cablesimultaneously delivers signals for conventional cable TV service aswell as Internet data to a customer location (such as a residentialhouse). At the customer premises, the cable line is typically split sothat the conventional cable television service is transmitted to one ormore set top boxes connected to one or more televisions, while theInternet data follows a separate line to a cable modem. The cable modemcan then provide Internet connectivity (wireless or physicalconnectivity) to multiple devices such as desktop computer,Voice-over-IP telephones, laptop computers, cellular telephones, tabletcomputers, etc.

A significant portion of television service content (usually deliveredby cable, satellite, or broadcast) is moving more and more towardsInternet Protocol (IP) or IP-based delivery mechanisms. There arevarious third-party services that provide movies, TV shows, and othermultimedia content via IP-based delivery. Cable television serviceproviders that also provide Internet connectivity (e.g. via cable modem)can also now provide a portion of television programming (including liveTV) through consumer operated computer applications (e.g. a softwareprogram provided by the cable operator that is downloaded and executeson that consumers home PC or mobile device). These consumer softwareapplications receive television programming via IP-based transferinstead of conventional television signaling. By way of a specificexample, a desktop computer or tablet computer can have an applicationinstalled that enables a user to select and view television broadcastssupplied from the cable TV service provider, including real-time or livetelevision service, that is streamed over the Internet and received inIP packets through that consumer's cable modem, as opposed to beingtransmitted to a set top box and decoded into conventional televisionsignals (e.g. HDMI signals). In other words, in addition to deliveringcable TV service to set top boxes, the cable service provider can alsostream cable television service over the Internet connection using IPpackets.

SUMMARY

The IP-based delivery of cable television service to a user's home ormobile device essentially provides a second or third (i.e., additional)TV for a given cable television customer. Such a television interfacecan be convenient such as when used with very portable wireless tabletcomputers as the television screen can easily move throughout thecustomer premises. With certain types of Internet service agreements,such IP-based cable television service can create billing problems sincethe IP packets that arrive into the consumer's cable modem are treated,for billing purposes, just like any other kind of data.

It is common for Internet service plans to vary a level of service andcorresponding price based on download/upload speeds in that pricing canreflect a given download speed range offered by the Internet serviceprovider. For example, a given ISP can charge a first monthly rate tohave an Internet connection of 15 Megabytes per second download speed,and then have a second monthly rate for providing a Internet connectionwith download speeds up to 50 Megabytes per second. With such data ratebilling plans or packages, there is usually unlimited datatransfer—subject to the speed limitations. Thus, such Internet serviceplans are speed-based.

Other types of Internet service plans can have consumption-based pricinginstead of, or in addition to, speed-based limitations. That is, othertypes of Internet service plans can base a periodic fee on a particularamount of data that can be downloaded/consumed within a given period oftime. This is also known as a consumption-based billing (CBB) model. Forexample, Internet service plans commonly have a monthly billing cycle.

While some plans allow for unlimited data transfer (subject to datatransfer or bandwidth rates), other plans can be limited to a particularamount of data that can be transferred per billing period, withunlimited speed or subject to a particular transfer speed limitation.For example, such plans can affix a price for data downloads up to 20Gigabytes (GB) per month, 50 GB per month, 500 GB per month, or anyother offered amount. If a user exceeds this amount of data transfer inthe given time period, they are billed additional amounts for overages.These additional amounts can become expensive.

Embodiments disclosed herein are based in part on the observation thatit is undesirable to have cable television content (e.g. TV shoes,movies, on-demand programming, etc.) provided by the cable serviceprovider (that could be watched on any conventional television via settop box reception at that consumers home) and viewed via an IP-basedinterface (e.g. streamed to the user's computer or mobile device throughthe cable modem), to count against any type of data bandwidthconsumption cap or limitation. That is, since the consumer could watchtelevision using his or her set top box and a conventional television,why should the user's be penalized by making a choice to watch that sameprogramming or content on his or her computer (the penalty being thatthe content is now being received as data packets that are countedagainst his or her monthly data limit or bandwidth limit).

Techniques disclosed herein include systems and methods for excludingspecific application traffic from customer consumption-based billingdata counts. Such exclusion can be executed in real time. In one exampleconfiguration, the system can group all devices or servers (i.e. contentdistribution network (CDN) servers) that provide the IP-TV service (orany managed service that provides content) into a well-defined block ofIP addresses (e.g. CDN addresses). The system then creates orestablishes classifiers on a Cable Modem Termination System (CMTS). TheCMTS is a head-end device that communicates and provides data andsignaling to individual consumer cable modems. The classifiers enablethe CMTS to identify different types of IP data flows or streams withinall the data packets being transmitted to (or from) a given cable modem.That is, the classifiers enable the CMTS to identify specific IP-packettraffic coming from that block of IP addresses (traffic transmitteddownstream towards a customer cable modem) or going to that block of IPaddresses (traffic transmitted upstream towards specific IP addresses).In response, the CMTS classifies that traffic into a separate dataservice flow or traffic flow that is then excluded (for billingpurposes) from other data transfer that is counted towards a consumersdata bandwidth or monthly transfer limit that is applied to thatconsumer's account. In other words, the system distinguishes someInternet traffic that is carrying CDN content that originates fromcertain known IP addresses from default Internet traffic (e.g. generalweb traffic, email, data, etc.). The exclusion of CDN traffic such asIP-based streaming television is done in these embodiments since thecustomer is already paying for the ability to watch this traffic with acoupled cable television service agreement. The system then essentiallytreats a tablet computer displaying cable television content as if thetablet computer were just another TV device in the customer's house.This billing exclusion can apply for any “managed service,” meaning aservice for which the customer already purchases.

One embodiment includes a content manager that executes a dataconsumption tracking and billing process or system for managing billingof consumption-based data billing plans. The content manager receives,at a Cable Modem Termination System (CMTS) or other device that feedsdata to a customer device such as modem (e.g. customer cable modem ormodem that works on media networks that are not “cable” networks, suchas optical networks, or hybrid coax/optical networks), Internet Protocol(IP) data packets having a destination address of the customer cablemodem. The CMTS is configured to forward the IP data packets to thecustomer cable modem via a first logical data service flow identifier,that is, a default setting is to send IP packets via the first logicaldata service flow. The customer cable modem corresponds to a customerservice account having both cable television service and cable Internetservice. The content manager examines packet headers of the IP datapackets received at the CMTS. In response to identifying a stream ofdata packets having a source IP address that matches an IP address froma predetermined set of IP addresses, the CMTS forwards that stream ofdata packets to the cable modem via a second logical data service flowidentifier instead of via the first logical data service flowidentifier. This predetermined set of IP addresses corresponding todevices that serve cable television content that is excluded from aconsumption-based data billing plan of the cable Internet service, suchas cable television programming already purchased as part of cabletelevision service. The content manager also transmits an IP DetailRecord (IPDR) towards a billing system that processes the customerservice account. The IPDR indicates a first data consumption count ofdata forwarded via the first logical data service flow identifier.

Accordingly, cable television and other managed services that areaccounted for separately or using other means can be delivered across IPnetworks to customer devices without being counted towards data usage onconsumption-based Internet service agreements.

Yet other embodiments herein include software programs to perform thesteps and operations summarized above and disclosed in detail below. Onesuch embodiment comprises a computer program product that has acomputer-storage medium (e.g., a non-transitory, tangible,computer-readable media, disparately located or commonly located storagemedia, computer storage media or medium, etc.) including computerprogram logic encoded thereon that, when performed in a computerizeddevice having a processor and corresponding memory, programs theprocessor to perform (or causes the processor to perform) the operationsdisclosed herein. Such arrangements are typically provided as software,firmware, microcode, code data (e.g., data structures), etc., arrangedor encoded on a computer readable storage medium such as an opticalmedium (e.g., CD-ROM), floppy disk, hard disk, one or more ROM or RAM orPROM chips, an Application Specific Integrated Circuit (ASIC), afield-programmable gate array (FPGA), and so on. The software orfirmware or other such configurations can be installed onto acomputerized device to cause the computerized device to perform thetechniques explained herein.

Accordingly, one particular embodiment of the present disclosure isdirected to a computer program product that includes one or morenon-transitory computer storage media having instructions stored thereonfor supporting operations such as: receiving, at a Cable ModemTermination System (CMTS), Internet Protocol (IP) data packets having adestination address of a customer cable modem, the CMTS being configuredto forward the IP data packets to the customer cable modem via a firstlogical data service flow identifier, the customer cable modemcorresponding to a customer service account having both cable televisionservice and cable Internet service; examining packet headers of the IPdata packets received at the CMTS; in response to identifying a streamof data packets having a source IP address that matches an IP addressfrom a predetermined set of IP addresses, forwarding the stream of datapackets to the cable modem via a second logical data service flowidentifier instead of via the first logical data service flowidentifier, the predetermined set of IP addresses corresponding todevices that serve cable television content that is excluded from aconsumption-based data billing plan of the cable Internet service; andtransmitting an IP Detail Record (IPDR) towards a billing system thatprocesses the customer service account, the IPDR indicating a first dataconsumption count of data forwarded via the first logical data serviceflow identifier. The billing system can utilize a naming convention foreach service flow to identify which flow or flows are to be counted ornot towards the customers consumption limit. The instructions, andmethod as described herein, when carried out by a processor of arespective computer device, cause the processor to perform the methodsdisclosed herein.

Other embodiments of the present disclosure include software programs toperform any of the method embodiment steps and operations summarizedabove and disclosed in detail below.

Of course, the order of discussion of the different steps as describedherein has been presented for clarity sake. In general, these steps canbe performed in any suitable order.

Also, it is to be understood that each of the systems, methods,apparatuses, etc. herein can be embodied strictly as a software program,as a hybrid of software and hardware, or as hardware alone such aswithin a processor, or within an operating system or within a softwareapplication, or via a non-software application such a person performingall or part of the operations. Example embodiments as described hereinmay be implemented in products and/or software applications such asthose manufactured by Time Warner Cable Inc., New York, N.Y.

As discussed above, techniques herein are well suited for use insoftware applications supporting billing for IP data service. It shouldbe noted, however, that embodiments herein are not limited to use insuch applications and that the techniques discussed herein are wellsuited for other applications as well.

Additionally, although each of the different features, techniques,configurations, etc. herein may be discussed in different places of thisdisclosure, it is intended that each of the concepts can be executedindependently of each other or in combination with each other.Accordingly, the present invention can be embodied and viewed in manydifferent ways.

Note that this summary section herein does not specify every embodimentand/or incrementally novel aspect of the present disclosure or claimedinvention. Instead, this summary only provides a preliminary discussionof different embodiments and corresponding points of novelty overconventional techniques. For additional details and/or possibleperspectives of the invention and embodiments, the reader is directed tothe Detailed Description section and corresponding figures of thepresent disclosure as further discussed below.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of theinvention will be apparent from the following more particulardescription of preferred embodiments herein as illustrated in theaccompanying drawings in which like reference characters refer to thesame parts throughout the different views. The drawings are notnecessarily to scale, with emphasis instead being placed uponillustrating the embodiments, principles and concepts.

FIG. 1 is a block diagram of a service flows within a cable Internetsystem according to embodiments herein.

FIG. 2 is a flowchart illustrating an example of a process supportingcontent management and billing according to embodiments herein.

FIGS. 3-4 are a flowchart illustrating an example of a processsupporting content management and billing according to embodimentsherein.

FIG. 5 is a flowchart illustrating an example of a process supportingcontent management and billing according to embodiments herein.

FIG. 6 is an example block diagram of a content manager and/or billingsystem operating in a computer/network environment according toembodiments herein.

DETAILED DESCRIPTION

Techniques disclosed herein include systems, methods and apparatus forexcluding specific application traffic from being counted as dataagainst a predetermine limit for customer consumption-based billing datacounts. This is useful for excluding traffic from consumption totalswhere the application traffic has been accounted for or is available tothe consumer using other means, such as through billing as a separate ordistinct service, though both services can appear on a single bill. Forexample a tablet computer can run a video software application that usesa high-speed data network (via a cable modem). This video applicationmay be included as part of a core video package associated with adistinct cable television service provider. As such, it may not bedesirable to bill a customer for traffic consumed and rendered to theuser by this video software application when such content is accountedfor separately. That is, the user could simply watch that same contenton his or her television without the television content using up orbeing counted towards bandwidth or data usage limits on his or her cablemodem traffic plan. Accordingly, the system provides accurateconsumption billing of customer traffic that is outside of any othermanaged services.

In general, the system segments and is able to identify customer trafficinto managed and unmanaged flows, and then instructs back officeconsumption management tools to ignore data flow counts from the managedflows for customer billing purposes. As an example, the system can groupall desired services (managed services such as CDN data streaming from aCDN server) into a common or central IP address block for correspondingapplication servers. A new Data Over Cable Service InterfaceSpecification (DOCSIS) service flow is defined for a customer modem. Thesystem uses a classifier that matches (i.e. identifies and records anamount of) any traffic to or from this common IP address block. Forexample, a video application server farm and content delivery networkcan all be assigned IP addresses from this common IP address block(within a specified range of addresses). By using this address block asa classifier to match on traffic either to or from this space, thesystem can direct or move this application specific traffic into aseparate DOCSIS service flow. With desired traffic segmented into aseparate flow, the system can instruct the back-office systems, such asIP Detail Record (IPDR) collectors or billing systems, to ignoreconsumption from this flow when calculating a customer's overallbandwidth consumption.

The usage record (IPDR in this example) can identify each logicalservice data flow using a unique naming convention. For example for datapackets that are to be counted towards customer data consumption, alogical data service flow can be named HSD_RES_250. This example namecan be used to track data usage for all packets that are to be countedtowards the total consumption for a high speed residential data servicehaving a maximum consumption of 250 GB per month for a given customer.When the customer cable modem initially boots up and is configured, thecable modem can provide a list of the logical data service flows to theCMTS. Each logical data service flow can have a predetermined name thatis recognizable by a billing system that determines customer data usage.As the customer requests data traffic such as data, video, or othermedia that is transmitted to the customer premises via the cable modem(i.e. via IP data packets), the CMTS can identify which logical dataservice flow that data traffic is associated with and can keep a countof the amount of data of each different logical data service flow type.Periodically (e.g. every 15 minutes), the CMTS can transmit the usagerecord (e.g. IPDR in this example) to a billing system. The billingsystem can quickly determine, using the unique naming conventions thathave been predefined for each logical data service flow, which logicaldata service flow (or flows) to exclude or include when calculatingcustomer data consumption. As an example, the billing system can countany data packets sent on the logical data service flow HSD_RES_250 (e.g.all customer data other than data used to transport on demand televisionshows watched on that users computer) against the total consumptionlimit for this customer while all other logical data service flows canbe ignored. In this manner, the usage record includes naming conventionsto respectively identify each logical data service flow. The billingsystem utilizes the naming conventions of respective logical dataservice flows to determine which data service flow to be counted or nottowards data usage corresponding to the customer device.

This technique can be extended to include other managed services tocustomers including but not limited to home security, video/content ondemand, WIFI roaming and third party applications/sites. Further detailsregarding DOCSIS service flows and classifiers can be found in U.S.patent application Ser. No. 13/074,634, filed on Mar. 29, 2011, andentitled “A System and Method for Assigning a Service Flow Classifier,”which is hereby incorporated by reference in its entirety. Now morespecifically and referring to FIG. 1, a block diagram illustrates cablemodem service flows for managed services traffic. Cable ModemTermination System (CMTS) 170 is a conventional device typically locatedat a headend or hubsite of a cable provider. CMTSs are configured toprovide high-speed data services, such as cable Internet or voice overInternet Protocol, to cable customers. A given CMTS typically providesdata services to multiple customer cable modems, such as cable modem 160or an Advanced Wireless Gateway (AWG). CMTS 170 is connected to customercable modem 160 via a hybrid fiber coax (HFC) 120 connection, whichprovides a high capacity data link.

Customer cable modem 160 is typically located at a customer's premises,such as at a user's condo within a building, a home, an office building,etc. This diagram shows the customer cable modem 160 connected to atelephone 109, a laptop computer 106, and a tablet computer 105. Notethat these are just exemplary customer devices that can be connected tothe customer cable modem 160. Also note that the connection to thecustomer cable modem 160 can be wired or wireless (e.g. via an 802.11based wireless communications protocol), and that the wireless router orother customer gateway device can sit between the end user devices andthe customer cable modem 160. The telephone device 109 is IP-based voicedelivery service as opposed to conventional circuit switched telephonesystems.

CMTS 170 is shown as connected to various resources. CMTS 170 connectsto voice network 125, which can include server computers to route andmanage telephone calls, and interface with various types of cellular andlandline telephone systems. CMTS 170 connects to the Internet 122 foressentially any content available online, such as news, websites, email,multimedia, and so forth. Content from network 122 is typically notprovided by or managed by a provider of the CMTS 170, such as a cabletelevision company. The provider of the CMTS 170, however, provides ormanages content 127. Such managed content can include cable televisioncontent 114, a home security service 115 (including video fromsurveillance cameras), and miscellaneous managed services 117.

The CMTS 170 can establish service flows 121-1 and 121-2 between theCMTS 170 and the customer cable modem 160. Each service flow is alogical flow. The system can create multiple data service flows. Forexample, as shown, there are separate service flows for dynamic voicedata (Voice-over-IP), for voice signaling, for cable modem controlmessaging, for high-speed Internet data, as well as for managed services(shown within the arrow outlines). By creating separate logical serviceflows, the CMTS 170 can separately count data sent or received on agiven data service flow. The CMTS 170 logs this data activity andgenerates an IP Detail Record (IPDR). This detail record identifies aparticular customer by MAC or IP address, contains a timestampindicating the interval for this record, and reports the amount of bytesconsumed on the network. The CMTS 170 collects IPDR information for eachservice flow that a customer is using. There can be specific serviceflows defined for voice signaling and for call bearer traffic as well ascontent preview services. Traffic that is not classified within aspecific service flow can be counted in a default service flow, such asthe high-speed Internet flow. It is this default service flow trafficthat can ultimately be billed to the customer as part of adata-consumption plan. The CMTS 170 can be configured to transfer IPDRsto an IP data collector 175 or other central collector, which can thenbe aggregated and transmitted to a cable service billing system 181.

A service flow can include a uni-directional flow of packets thatprovides a certain quality of service (QoS). In addition to QoS, thebilling system/IPDR collector can be instructed to count or not countbytes of a particular service flow for billing purposes. A classifiercan include using a pattern-matching rule that identifies the trafficthat should use a particular service flow. Classifiers can identifytraffic based upon source/destination MAC/IP addresses,source/destination port numbers, Type of Service (ToS) bits (priority),IP Protocol type and other values in the IP packet header. Eachclassifier can also have a priority associated with it to instruct theCMTS 170 in the proper order to evaluate classifiers for placement intothe desired service flow. In some embodiments, multiple classifiers canbe configured to all point to a single service flow. A service flow iscreated when a cable modem comes online (powered on). While the customercable modem is turned on, it provisions itself and connects to the CMTS.

In some specific embodiments, classifiers and the flows can be definedin a configuration file that the cable modem receives when it boots. Aserver can generate those configuration files that define all thedifferent IP blocks or IP groups or a list of individual IP address thatshould be matched and identified as part of the content data networkflow or “managed services” flow. After receiving these configurationfiles, the cable modem then exchanges its registration with the CMTS andprovides this to the CMTS as part of the DOCSIS protocol. Note that theconfiguration file can be transmitted to the cable modem, after whichthe cable modem exchanges the information in the configuration file withthe CMTS as part of a registration process.

By way of a more specific example, consider that the customer cablemodem 160 is tied to a customer account that purchases both cable-basedInternet service and cable television service. Conventionally this isreferred to as “bundling” or grouping services.

A VOIP service can also be grouped into the customer account. Suchgrouping enables the customer to pay for multiple services using asingle account or invoice. Consider also that tablet computer 105contains a cable television viewing application for viewing cabletelevision programming via IP-based delivery through the cable modem160. Note that this customer would have a separate connection to set topboxes at televisions because the conventional cable television signalsdo not pass through the customer cable modem 160.

An end user launches a cable television viewing application on tabletcomputer 105. In response, tablet computer 105 transmits a request forcable television content to access managed content 127. This requestfollows path 128 via customer cable modem 160 using a Managed ServiceFlow, through CMTS 170 to access cable television content 114. Inresponse, one or more servers within managed content 127 begintransmitting cable television content (or other managed content) asshown by path 129. When corresponding data packets arrive at the CMTS170, a classifier examines the data packets and determines that the datapackets originate from a particular IP address block. As a response, theclassifier directs (or redirects) those data packets to a managedservice/content flow identifier, and then to the tablet computer 105 viathe customer cable modem 160. By routing such data packets on a separatedata service flow, a separate IPDR can be created specifically for thisflow.

FIG. 6 illustrates an example block diagram of a content manager 140operating in a generic computer/network environment according toembodiments herein. In summary, FIG. 6 shows computer system 149displaying a graphical user interface 133 that provides aconsumption-based billing system interface. Computer system 149 canconnect to a remote server for processing assistance. Computer systemhardware aspects of FIG. 6 will be described in more detail following adescription of the flow charts.

Functionality associated with content manager 140 will now be discussedvia flowcharts and diagrams in FIG. 2 through FIG. 5. For purposes ofthe following discussion, the content manager 140 or other appropriateentity (such as the CMTS or customer cable modem) performs steps in theflowcharts.

Now describing embodiments more specifically, FIG. 2 is a flow chartillustrating embodiments disclosed herein. In step 210, content manager140 receives, at a Cable Modem Termination System (CMTS), InternetProtocol (IP) data packets having a destination address of a customercable modem. Having a destination address of the customer cable modemmeans that the destination address either identifies the cable modemitself or that the destination address identifies customer-premisesequipment (CPE) that is accessed via the cable modem (with the cablemodem being a type of gateway to one or more customer-premisesequipment). Note that the cable modem can be directly linked to the CPE,or be directly linked to a router (such as a wireless home router) thatin turn provides data connectivity to the CPE.

The CMTS is configured to forward the IP data packets to the customercable modem via a first logical data service flow identifier, such as adefault service flow for Internet traffic. The customer cable modemcorresponds to a customer service account having both cable televisionservice and cable Internet service, such a bundled package of services.Note that the destination address of a customer cable modem can includethe cable modem, any associated router or AWG, or end user deviceswithin a local network. In other words, having a destination address ofthe customer cable modem refers to data packets that must be forwardedor routed to or through a particular customer cable modem.

In step 220, the content manager 140 examines packet headers of the IPdata packets received at the CMTS. This examination can identify IP orMAC address.

In step 230, in response to identifying a stream of data packets havinga source IP address that matches an IP address from a predetermined setof IP addresses (or in response to identifying predetermined informationin the packet header), the CMTS forwards the stream of data packets tothe cable modem via a second logical data service flow identifierinstead of via the first (default) logical data service flow identifier.This predetermined set of IP addresses corresponds to devices that servecable television content that is excluded from a consumption-based databilling plan of the cable Internet service. Note that the set of IPaddress can include a block or range of IP addresses, or a list ofspecific IP address to exclude.

In step 240, the CMTS transmits an IP Detail Record (IPDR) towards abilling system that processes the customer service account. The IPDRindicating a first data consumption count of data forwarded via thefirst logical data service flow identifier. This can be transmittedtowards a billing system by first being transmitted to a collector orintermediate aggregation system before be transmitted to the billingsystem.

FIGS. 3-4 include a flow chart illustrating additional and/oralternative embodiments and optional functionality of the contentmanager 140 as disclosed herein.

In step 210, content manager 140 receives, at a Cable Modem TerminationSystem (CMTS), Internet Protocol (IP) data packets having a destinationaddress of a customer cable modem. The CMTS is configured to forward theIP data packets to the customer cable modem via a first logical dataservice flow identifier, such as a default service flow for Internettraffic. The customer cable modem corresponds to a customer serviceaccount having both cable television service and cable Internet service,such a bundled package of services.

In step 212, a provider of the cable television service is a sameprovider of the cable television content transmitted via the cableInternet service from originating from the predetermined set of IPaddresses. In other words, one particular entity provides cabletelevision (or other managed service) in addition to Internetconnectivity, such as with a bundled service plan.

In step 220, the content manager 140 examines packet headers of the IPdata packets received at the CMTS.

In step 230, in response to identifying a stream of data packets havinga source IP address that matches an IP address from a predetermined setof IP addresses, the CMTS forwards the stream of data packets to thecable modem via a second logical data service flow identifier instead ofvia the first (default) logical data service flow identifier. Thispredetermined set of IP addresses corresponds to devices that servecable television content that is excluded from a consumption-based databilling plan of the cable Internet service. By forwarding the stream ofdata packets to the cable modem via a second logical data service, theCMTS tracks the amount of data packets for that stream and records thisinformation in a usage record. Each logical data service flow can have aunique name and naming conventions can be used within the usage records.Thus, data that is to be counted against a total amount of consumptionallowed for that customer can be tracked by the CMTS and the logicaldata service flow name can be identified by the billing system. Thebilling system periodically receives the usage record and can use thepredefined named of the logical data service flow to quickly determinewhat service flow or flows to exclude or not from being counted againstthe customers total data usage.

In step 232, the content manager 140 forwards the stream of data packetstowards a cable television viewing application installed on a wirelesstablet computer, desktop computer, cell phone, or other end user device.

In step 234, the first logical data service flow identifier and secondlogical data service flow identifier are both established according toData Over Cable Service Interface Specification (DOCSIS).

In step 240, the CMTS transmits an IP Detail Record (IPDR) towards abilling system that processes the customer service account. The IPDRindicating a first data consumption count of data forwarded via thefirst logical data service flow identifier.

In step 242, the content manager transmits the IPDR to an IPDR collectorin communication with the billing system. Such an IPDR collector canaggregate multiple IPDRs for an individual customer.

In step 243, the IPDR indicates a second data consumption count of dataforwarded via the second logical data service flow identifier, and thebilling system ignores the second data consumption count when processingdata usage of cable Internet service of the customer service account.Thus, while data counts can be recorded and reported for each or anyservice flow, only one or more specific data service flows are countedfor data-consumption billing purposes.

In step 250 the content manager 140 receives, at the CMTS, customer IPdata packets having a source address of Customer-Premises Equipment(CPE) and received via the customer cable modem, the CMTS beingconfigured to forward the customer IP data packets via the first logicaldata service flow identifier. Thus, the system can count and therebyexclude traffic going in either direction—either from the CMTS to thecustomer cable modem, or from the customer cable modem to the CMTS.

In step 260, in response to identifying customer IP data packetsreceived from the customer cable modem that have a destination IPaddress that matches an IP address from the predetermined set of IPaddresses, the content manager forwards the customer IP data packets viathe second logical data service flow identifier instead of via the firstlogical data service flow identifier.

In step 270, in response to identifying a second stream of data packetshaving source IP address matching at least one IP address from a secondpredetermined set of IP addresses, the content manager forwards thesecond stream of data packets to the cable modem via a third logicaldata service flow identifier instead of via the first logical dataservice flow identifier. For example, a particular customer might alsobe paying for a VOIP service or some other type of managed service,which may not be desired to be included in any other service flow.Alternatively, this second predetermined set of IP addressescorresponding to server computers that provide a home security servicevia the customer cable modem, the home security service being excludedfrom the consumption- based data billing plan of the cable Internetservice. Note that VOIP service may be separately accounted for usingthe VOIP protocol instead of using IP blocks.

In step 280, in response to identifying that the customer cable modem isphysically located within a first geographical region, the contentmanager adds additional IP addresses to the predetermined set of IPaddresses based on the first geographical region such that contenttransmitted from the additional IP address is forwarded via the secondlogical data service flow. For example, if the system identifies that acustomer cable modem is located in New York state, then IP addresses fora set of servers designated for New York state can be added to the setof addresses.

FIG. 5 includes a flow chart illustrating additional and/or alternativeembodiments and optional functionality of the content manager 140 asdisclosed herein.

In step 510, a billing system receives an IP Detail Record (IPDR)indicating data usage corresponding to a customer cable modem. This IPDRhaving been logged by a Cable Modem Termination System (CMTS) thatprovides cable Internet service to the customer cable modem byforwarding Internet Protocol (IP) data packets via logical data serviceflows. The IPDR identifies a first amount of data traffic using a firstlogical data service flow identifier. The IPDR also identifies a secondamount of data traffic using a second logical data service flowidentifier. The CMTS uses the second logical data service flowidentifier when forwarding a stream of data packets destined for thecustomer cable modem and having a source IP address that matches an IPaddress from a predetermined set of IP addresses. The predetermined setof IP addresses corresponds to devices that serve cable televisioncontent. The billing system managing configured to bill a customerservice account corresponding to the cable modem. The customer serviceaccount purchasing both cable television service and cable Internetservice, with the cable Internet service having consumption-based databilling plan.

In step 520, the system include data counts from the first logical dataservice flow identifier when calculating data usage for theconsumption-based data billing plan.

In step 530, the system excludes data counts from the second logicaldata service flow identifier when calculating data usage for theconsumption-based data billing plan.

The CMTS can thus forwarding the stream of data packets to the cablemodem via the second logical data service flow identifier instead of viathe first logical data service flow identifier. Also, the CMTS canforward the stream of data packets towards a cable television viewingapplication installed on a wireless tablet computer. The first logicaldata service flow identifier and second logical data service flowidentifier are both established according to Data Over Cable ServiceInterface Specification (DOCSIS). Additionally, the CMTS can use a thirdlogical data service flow identifier when forwarding a second stream ofdata packets destined for the customer cable modem and having a sourceIP address that matches at least one IP address from a secondpredetermined set of IP addresses, instead of using the first logicaldata service flow identifier. The second predetermined set of IPaddresses can corresponds to server computers that provide a homesecurity service corresponding to the customer cable modem, with thehome security service being excluded from the consumption-based databilling plan of the cable Internet service.

Yet other embodiments can include deep packet inspection (DPI) todistinguish managed service content from general high-speed traffic.Executing deep packet inspection (DPI), however, is intrusive andexpensive, and thus not as preferable as techniques previously disclosedherein to identify actual content within data packets. In addition totraffic separation, the system can also incorporate traffic segmentation(such as be using SSIDs) to even further separate traffic counts on thecustomer end, or to enable such a billing system during roaming onanother customer's WIFI network. For example, a first user havingbundled service visits a second user having only consumption-basedInternet service. If the first user watches cable television content onthe second user's home network, then corresponding data counts can beexcluded from data usage counted against/towards the second user.

In another embodiment, techniques include a method, system or apparatusfor managing billing of consumption-based data billing plans. Thisincludes receiving data packets having a destination address of acustomer device. These data packets are received at a contentdistribution device that delivers content to multiple customer premises.Such a device can be a network server(s), network interface device,CMTS, etc. The customer device can include a personal computer, portablecomputer, cell phone, cable modem, DSL modem, optical network unit(ONU), router, and so forth. The content distribution device isconfigured to forward the data packets to the customer device via afirst logical data service flow identifier of a plurality of logicaldata service flow identifiers. The content distribution device examinespacket headers of the data packets received at the content distributiondevice. In response to identifying a stream of data packets havingpredetermined information in the packet header, the content distributiondevice forwards the stream of data packets to the customer device via asecond logical data service flow identifier instead of the first logicaldata service flow identifier. The predetermined information identifiespackets that are excluded from a consumption-based data billing plan,which can be associated with the customer device. The contentdistribution device transmits a usage record to a billing system thatprocesses billing for the customer device or an account associated withthe customer device. The usage record indicates a data consumption countfor at least one of the plurality of logical data service flowidentifiers.

Forwarding the stream of data packets to the customer device via thesecond logical data service flow can include forwarding the stream ofdata packets towards a television viewing application installed on aportable computing device, such as a tablet computer, smart phone, etc.The content distribution device can deliver both television content andInternet connectivity to the multiple customer premises using hybridfiber coax (HFC) broadband network, Fiber-to-the-premises fiber opticnetwork, or other similar networks. The content distribution device canbe embodied as a Cable Modem Termination System (CMTS), DigitalSubscriber Line Access Multiplexer (DSLAM), Optical Network Terminal(ONT), Optical Network Unit (ONU) or Optical Line Terminal (OLT). Notethat a provider of television service can be a same provider oftelevision content transmitted via Internet service originating from apredetermined set of IP addresses. In other words, a given InternetService provider not only provides Internet connectivity, but alsoserves multimedia content (instead of simply providing connectivity tothird party content.

The content distribution device can receive customer data packets havinga source address of Customer-Premises Equipment (CPE), and which packetsare received via the customer device. The content distribution devicecan be configured to forward the customer data packets via the firstlogical data service flow identifier. In response to identifyingcustomer data packets received from the customer device, with those datapackets having a destination address that matches an address from apredetermined set of addresses, the content distribution device forwardsthe customer data packets via the second logical data service flowidentifier instead of the first logical data service flow identifier.

Continuing with FIG. 6, the following discussion provides a basicembodiment indicating how to carry out functionality associated with thecontent manager 140 as discussed above. It should be noted, however,that the actual configuration for carrying out the content manager 140can vary depending on a respective application. For example, computersystem 149 can include one or multiple computers that carry out theprocessing as described herein.

In different embodiments, computer system 149 may be any of varioustypes of devices, including, but not limited to, a cell phone, apersonal computer system, desktop computer, laptop, notebook, or netbookcomputer, mainframe computer system, handheld computer, workstation,network computer, router, network switch, bridge, application server,storage device, a consumer electronics device such as a camera,camcorder, set top box, mobile device, video game console, handheldvideo game device, or in general any type of computing or electronicdevice.

Computer system 149 is shown connected to display monitor 130 fordisplaying a graphical user interface 133 for a user 136 to operateusing input devices 135. Repository 138 can optionally be used forstoring data files and content both before and after processing. Inputdevices 135 can include one or more devices such as a keyboard, computermouse, microphone, etc.

As shown, computer system 149 of the present example includes aninterconnect 143 that couples a memory system 141, a processor 142, I/Ointerface 144, and a communications interface 145.

I/O interface 144 provides connectivity to peripheral devices such asinput devices 135 including a computer mouse, a keyboard, a selectiontool to move a cursor, display screen, etc.

Communications interface 145 enables the content manager 140 of computersystem 149 to communicate over a network and, if necessary, retrieve anydata required to create views, process content, communicate with a user,etc. according to embodiments herein.

As shown, memory system 141 is encoded with content manager 140-1 thatsupports functionality as discussed above and as discussed furtherbelow. Content manager 140-1 (and/or other resources as describedherein) can be embodied as software code such as data and/or logicinstructions that support processing functionality according todifferent embodiments described herein.

During operation of one embodiment, processor 142 accesses memory system141 via the use of interconnect 143 in order to launch, run, execute,interpret or otherwise perform the logic instructions of the contentmanager 140-1. Execution of the content manager 140-1 producesprocessing functionality in content manager process 140-2. In otherwords, the content manager process 140-2 represents one or more portionsof the content manager 140 performing within or upon the processor 142in the computer system 149.

It should be noted that, in addition to the content manager process140-2 that carries out method operations as discussed herein, otherembodiments herein include the content manager 140-1 itself (i.e., theun-executed or non-performing logic instructions and/or data). Thecontent manager 140-1 may be stored on a non-transitory, tangiblecomputer-readable storage medium including computer readable storagemedia such as floppy disk, hard disk, optical medium, etc. According toother embodiments, the content manager 140-1 can also be stored in amemory type system such as in firmware, read only memory (ROM), or, asin this example, as executable code within the memory system 141.

In addition to these embodiments, it should also be noted that otherembodiments herein include the execution of the content manager 140-1 inprocessor 142 as the content manager process 140-2. Thus, those skilledin the art will understand that the computer system 149 can includeother processes and/or software and hardware components, such as anoperating system that controls allocation and use of hardware resources,or multiple processors.

Those skilled in the art will also understand that there can be manyvariations made to the operations of the techniques explained abovewhile still achieving the same objectives of the invention. Suchvariations are intended to be covered by the scope of this invention. Assuch, the foregoing description of embodiments of the invention are notintended to be limiting. Rather, any limitations to embodiments of theinvention are presented in the following claims.

1. A method comprising: receiving first data packets over acommunication link from a first source, the first data packets destinedfor delivery to a communication device operated by a user in a networkenvironment, the first data packets assigned delivery information tofacilitate conveyance of the first data packets over the communicationlink to the communication device; examining the delivery informationassigned to the first data packets, the delivery information indicatingthat the first data packets are received from the first source; andutilizing the delivery information assigned to the first data packets asa basis to exclude the first data packets from being included in a datadelivery count assigned to the user, the data delivery countrepresenting an amount of data conveyed to the communication device overthe communication link.
 2. The method as in claim 1, wherein content inthe first data packets is alternatively available to the user over thecommunication link from a second source.
 3. The method as in claim 2,wherein the first data packets are excluded from inclusion in the datadelivery count assigned to the user since the content is available tothe user over the communication link from the second source.
 4. Themethod as in claim 3, wherein the user subscribes to a first servicefrom a service provider to have access to the Internet over a first dataflow of the communication link; and wherein the user subscribes to asecond service from the service provider to receive the content over asecond data flow of the communication link from the second source. 5.The method as in claim 1, wherein the content is available to the userover a first data flow of the communication link from the first sourcebased on a first service agreement between the service provider and theuser; and wherein the content is available to the user over a seconddata flow of the communication link from the second source based on asecond service agreement between the service provider and the user. 6.The method as in claim 5, wherein the first data packets are excludedfrom inclusion in the data delivery count assigned to the user since thecontent is available to the user from the second source.
 7. The methodas in claim 6, wherein the data delivery count represents an amount ofdata conveyed over the first data flow.
 8. The method as in claim 1,wherein the data delivery count represents a billable data count inwhich the user pays a supplemental fee to retrieve data over thecommunication link.
 9. The method as in claim 2 further comprising:providing the user use of the communication link as part of subscriptionservices in which the user, via the subscription services, is able toretrieve content from both the first source and the second source. 10.The method as in claim 9, wherein the subscription services supportconveyance of data over a first data flow and a second data flow,conveyance of data over the first data flow excluded from billablecontent consumption by the user, conveyance of data over the second dataflow included in billable content consumption by the user.
 11. Themethod as in claim 1, wherein examining the delivery informationincludes obtaining a network address indicating the first source fromwhich the data packets are transmitted to the communication device. 12.The method as in claim 11, wherein utilizing the delivery informationassigned to the first data packets as a basis to exclude the first datapackets from being counted towards content consumption to the user overthe communication link includes: classifying the first data packets intoa data flow in which corresponding data conveyed over the data flow isexcluded from being included in the data delivery count.
 13. A systemcomprising; a communication link; and communication hardware operable toprovide a communication device operated by a user access to multiplecontent delivery sources over the communication link, the communicationhardware operable to: receive first data packets from a first source ofthe multiple content delivery sources, the first data packets destinedfor delivery to the communication device operated by the user, the firstdata packets assigned delivery information to facilitate conveyance ofthe first data packets over the communication link to the communicationdevice; examine the delivery information assigned to the first datapackets, the delivery information indicating that the first data packetsare received from the first source; and utilize the delivery informationassigned to the first data packets as a basis to exclude the first datapackets from being included in a data delivery count assigned to theuser, the data delivery count representing an amount of data conveyed tothe communication device over the communication link.
 14. The system asin claim 13, wherein content in the first data packets is alternativelyavailable to the user over the communication link from a second sourceof the multiple content delivery sources.
 15. The system as in claim 14,wherein the first data packets are excluded from inclusion in the datadelivery count assigned to the user since the content is available tothe user over the communication link from the second source.
 16. Thesystem as in claim 15, wherein the user subscribes to a first servicefrom a service provider to have access to the Internet over a first dataflow of the communication link; and wherein the user subscribes to asecond service from the service provider to receive the content over asecond data flow of the communication link from the second source. 17.The system as in claim 14, wherein the content is available to the userover a first data flow of the communication link from the first sourcebased on a first service agreement between the service provider and theuser; and wherein the content is available to the user over a seconddata flow of the communication link from the second source based on asecond service agreement between the service provider and the user. 18.The system as in claim 17, wherein the first data packets are excludedfrom inclusion in the data delivery count assigned to the user since thecontent is available to the user over the second data flow.
 19. Thesystem as in claim 14, wherein the communication hardware is furtheroperable to: provide the user use of the communication link as part ofsubscription services in which the user, via the subscription services,is able to retrieve content from both the first source and the secondsource.
 20. Non-transitory computer-readable storage media havinginstructions stored thereon, the instructions, when carried out bycomputer processor hardware, cause the computer processor hardware to:receive first data packets over a communication link from a firstsource, the first data packets destined for delivery to a communicationdevice operated by a user in a network environment, the first datapackets assigned delivery information to facilitate conveyance of thefirst data packets over the communication link to the communicationdevice; examine the delivery information assigned to the first datapackets, the delivery information indicating that the first data packetsare received from the first source; and utilize the delivery informationassigned to the first data packets as a basis to exclude the first datapackets from being included in a data delivery count assigned to theuser, the data delivery count representing an amount of data conveyed tothe communication device over the communication link.